Skip to main content

Incident Reports (???)

This directory contains a record of all the operational incidents that have occurred within our infrastructure. Proper documentation of each incident helps the team in the following ways:

  • Understanding Root Causes: Detailed reports allow us to understand what caused the incident.
  • Pattern Recognition: Over time, we might see patterns that hint at deeper infrastructure or code issues.
  • Improved Response: By understanding past incidents, we can respond to new ones more effectively.
  • Knowledge Transfer: New team members can refer to these reports to understand past issues.
TODO

The incident reports seem somewhat redundant now that a newer system is in place. While I understand the desire to archive these older records here, they can still be accessed using the repo tag Pre-Docusaurus. Please see the box below as a reminder for readers. Perhaps we should include a simple page in the root of this folder that notes the existence of these older reports.

Older incident report

Older incident reports that are not available in current tracking systems are still accessible using the repo tag Pre-Docusaurus.

How to Document an Incident​

  1. Create a New File: For each new incident, create a new markdown file with a descriptive name. Format: YYYYMMDD_description.md
  2. Follow the Template: Use the template provided in template_incident.md as a reference.
  3. Link in This Readme: Add a link to the new incident report in the list below.

Incident List​

(Add more incidents as they occur, newest first)

Last updated on by Warren Anderson